Method, apparatus, and computer program product for system resource volume prediction

ABSTRACT

Embodiments of the present invention provide methods, systems, apparatuses, and computer program products for predicting system resource volumes for future network time intervals based upon predicted likelihoods of termination transactions for the future network time interval.

CROSS REFERENCE TO RELATED APPLICATIONS

The present application claims priority to U.S. Provisional Application Ser. No. 62/440,277, titled “METHOD, APPARATUS, AND COMPUTER PROGRAM PRODUCT FOR SYSTEM RESOURCE VOLUME PREDICTION,” filed Dec. 29, 2016, the contents of which are incorporated herein by reference in their entirety.

BACKGROUND

Various systems are configured to manage and allocate system resources. Applicant has identified a number of deficiencies and problems associated with predicting and allocating system resources for any given network time period. Through applied effort, ingenuity, and innovation, many of these identified problems have been solved by developing solutions that are included in embodiments of the present invention, many examples of which are described in detail herein.

BRIEF SUMMARY

This specification relates to system resource prediction based on a machine learning model.

In general, one innovative aspect of the subject matter described in this specification can be embodied in methods, systems, apparatuses, and computer program products for predicting system resource volumes for future network time intervals. In one embodiment a server is provided that, when executing instructions using its processor, receives first transaction data and second transaction data. In embodiments, the first transaction data comprises a first timestamp and the second transaction data comprises a second timestamp. In embodiments, the first and second transaction data are associated with a device rendered object of the plurality of device rendered objects, and the second transaction occur subsequent to the first transaction. In embodiments, the server is further configured to receive system transaction data, where the system transaction data comprises a network time interval and a system transaction count occurring during the network time interval. In embodiments, the server is further configured to determine, based on the first transaction data, the second transaction data, and the system transaction data, a first prediction value that indicates a programmatically expected number of transaction terminations for a future network time interval.

Other embodiments of this aspect include corresponding systems, apparatus, and computer programs, configured to perform the actions of the methods, encoded on computer storage devices.

Particular embodiments of the subject matter described in this specification can be implemented so as to realize one or more of the following advantages.

Embodiments of the present disclosure realize significantly increased accuracy of a predictive model that delivers a programmatically determined required system resource threshold volume. Embodiments of the present disclosure further ensure a data store associated with system resource volume does not fall below a programmatically determined threshold. Embodiments of the present disclosure enable reduced processing power and time required to programmatically determine required system resource threshold volume and to maintain the data store at the programmatically determined threshold.

The details of one or more embodiments of the subject matter described in this specification are set forth in the accompanying drawings and the description below. Other features, aspects, and advantages of the subject matter will become apparent from the description, the drawings, and the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

Having thus described the invention in general terms, reference will now be made to the accompanying drawings, which are not necessarily drawn to scale, and wherein:

FIG. 1 is an overview of an example system that can be used to practice embodiments of the present invention;

FIG. 2 is an exemplary schematic diagram of a computing entity according to one embodiment of the present invention;

FIG. 3 is an exemplary data flow illustrating interactions between a server, one or more network asset requester devices, and one or more network asset provider devices;

FIGS. 4, 5A, and 5B are flow charts illustrating various procedures and operations that may be completed in accordance with various embodiments of the present invention; and

FIG. 6 illustrates an exemplary random forest model.

DETAILED DESCRIPTION OF VARIOUS EMBODIMENTS

Various embodiments of the present invention now will be described more fully hereinafter with reference to the accompanying drawings, in which some, but not all embodiments of the inventions are shown. Indeed, these inventions may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will satisfy applicable legal requirements. The term “or” is used herein in both the alternative and conjunctive sense, unless otherwise indicated. The terms “illustrative” and “exemplary” are used to be examples with no indication of quality level. Like numbers refer to like elements throughout.

Overview

Various embodiments of the invention generally relate to system resource prediction based on a machine learning model.

In one example, a resource management system may supply a data set to a learning machine or algorithm. The learning machine or algorithm may then determine which features or attributes associated with a device rendered object of a transaction correlate to a high likelihood that a subsequent termination transaction will occur in a given network period and which features or attributes correlate to a low likelihood. Accordingly, the learning machine may select a subset of features or attributes for training. Once the learning machine or algorithm is trained, live data associated with a new transaction may be input and the learning machine or algorithm may then classify the transaction as having a high likelihood of resulting in a termination transaction in a given network period or not. As such, the system may allocate necessary resources for a future network period, the resources required for correcting termination transactions.

Definitions

As used herein, the terms “data,” “content,” “information,” and similar terms may be used interchangeably to refer to data capable of being transmitted, received, and/or stored in accordance with embodiments of the present invention. Thus, use of any such terms should not be taken to limit the spirit and scope of embodiments of the present invention. Further, where a computing device is described herein to receive data from another computing device, it will be appreciated that the data may be received directly from another computing device or may be received indirectly via one or more intermediary computing devices, such as, for example, one or more servers, relays, routers, network access points, base stations, hosts, and/or the like, sometimes referred to herein as a “network.” Similarly, where a computing device is described herein to send data to another computing device, it will be appreciated that the data may be sent directly to another computing device or may be sent indirectly via one or more intermediary computing devices, such as, for example, one or more servers, relays, routers, network access points, base stations, hosts, and/or the like.

As used herein, the term “resource management system” may include a system that is accessible via one or more computing devices and that is operable to transmit data comprising executable instructions that, when executed on a computing device, can render a device rendered object for display by the device. A device rendered object can, for example, be an electronic representation of a digital promotion or marketing service provided by one or more providers that are offering one or more instruments that are redeemable for goods, services, experiences and/or the like. In some examples, the system may take the form of a server enabling transactions related to redemption of promotions associated with device rendered objects, processing of financial transactions associated with device rendered objects, and/or the like. As such, the system is, in some example embodiments, configured to present one or more device rendered objects that display promotions via one or more impressions, accept payments for promotions from consumers, issue instruments upon acceptance of an offer or a promotion, participate in redemption, generate rewards, provide a point of sale device or service, issue payments to providers and/or otherwise participate in the exchange of goods, services or experiences for currency, value and/or the like. The system is also, in some example embodiments, configured to enable object parameter analysis, whereby parameters associated with device rendered objects can be optimally selected, including parameter analytics and the like.

As used herein, the term “network asset provider” may be used to refer to a network actor capable of providing a network asset to another computing device. A network asset may be a set of instructions that, when executed by a computing device, renders an instrument redeemable for a network asset. An example of a network asset provider may be a provider or a merchant.

As used herein, the term “network asset requester” may be used to refer to a requester for network assets that may be purchased, consumed, or redeemed by the network asset requester. Examples of a network asset requester may include a consumer.

As used herein, the terms “provider” and “merchant” may be used interchangeably and may include, but are not limited to, a business owner, consigner, shopkeeper, tradesperson, vendor, operator, entrepreneur, agent, dealer, organization or the like that is in the business of providing a good, service or experience to a consumer, facilitating the provision of a good service or experience to a consumer and/or otherwise operating in the stream of commerce. The “provider” or “merchant” need not actually market a product or service via the promotion and marketing service, as some merchants or providers may utilize the promotion and marketing service only for the purpose of gathering marketing information, demographic information, or the like.

As used herein, the term “consumer” should be understood to refer to a recipient of goods, services, promotions, media, or the like provided by the promotion and marketing service and/or a merchant. Consumers may include, without limitation, individuals, groups of individuals, corporations, other merchants, and the like.

As used herein, the terms “network asset” and “device rendered object” may be used interchangeably to mean an electronic representation of or an instrument redeemable for a digital promotion or marketing service provided by one or more providers that are offering one or more instruments that are redeemable for goods, services, experiences and/or the like. In some examples, the system may take the form of a server enabling transactions related to redemption of promotions associated with device rendered objects, processing of financial transactions associated with device rendered objects, and/or the like. As such, the system is, in some example embodiments, configured to present one or more device rendered objects that display promotions via one or more impressions, accept payments for promotions from consumers, issue instruments upon acceptance of an offer or a promotion, participate in redemption, generate rewards, provide a point of sale device or service, issue payments to providers and/or otherwise participate in the exchange of goods, services or experiences for currency, value and/or the like. The system is also, in some example embodiments, configured to enabling object parameter analysis, whereby parameters associated with device rendered objects can be optimally selected, including parameter analytics, and the like. Examples of device rendered objects or network assets may include promotions or deals.

As used herein, the term “promotion” may include, but is not limited to, any type of offered, presented or otherwise indicated reward, discount, coupon, credit, deal, incentive, discount, media or the like that is indicative of a promotional value or the like that upon purchase or acceptance results in the issuance of an instrument that may be used toward at least a portion of the purchase of particular goods, services and/or experiences defined by the promotion. Promotions may have different values in different contexts. For example, a promotion may have a first value associated with the cost paid by a consumer, known as an “accepted value.” When redeemed, the promotion may be used to purchase a “promotional value” representing the retail price of the goods. The promotion may also have a “residual value,” reflecting the remaining value of the promotion after expiration. Although consumers may be primarily focused on the accepted and promotional value of the promotion, a promotion may also have additional associated values. For example, a “cost value” may represent the cost to the merchant to offer the promotion via the promotion and marketing service, where the promotion and marketing service receives the cost value for each promotion sold to a consumer. The promotion may also include a “return on investment” value, representing a quantified expected return on investment to the merchant for each promotion sold.

For example, consider a device rendered object that includes instructions to cause the rendering at a computing device of a promotion offered by the system for a digital instrument redeemable for a $50 meal promotion for a transaction value of $25 at a particular restaurant. In this example, $25 would be the transaction value and an associated digital amount is debited from a data store associated with a device initiating the transaction. A consumer associated with the device initiating the transaction would then be able to redeem the promotion at the restaurant for $50 applied toward their meal check. This $50 would be the promotional value of the promotion. If the consumer did not use the promotion before expiration, the consumer might be able to obtain a refund of $22.50, representing a 10% fee to recoup transaction costs for the merchant and/or promotion and marketing service. This $22.50 would be the residual value of the promotion. If the promotion and marketing service charged the merchant $3.00 to offer the promotion, the $3.00 fee would be the “cost value.” The “return on investment” value of the promotion might be dynamically calculated by the promotion and marketing service based on the expected repeat business generated by the marketing of the promotion, the particular location, the demographics of the consumer, and the like. For example, the return on investment value might be $10.00, reflecting the long term additional profit expected by the merchant as a result of bringing in a new customer through use of a promotion.

Promotions may be provided to consumers and redeemed via the use of an “instrument.” Instruments may represent and embody the terms of the promotion from which the instrument resulted. For example, instruments may include, but are not limited to, any type of physical token (e.g., magnetic strip cards or printed barcodes), virtual account balance (e.g., a promotion being associated with a particular user account on a merchant website), secret code (e.g., a character string that can be entered on a merchant website or point-of-sale), tender, electronic certificate, medium of exchange, voucher, or the like, which may be used in a transaction for at least a portion of the purchase, acquisition, procurement, consumption or the like of goods, services and/or experiences as defined by the terms of the promotion.

In some examples, the instrument may take the form of tender that has a given value that is exchangeable for goods, services and/or experiences and/or a reduction in a purchase price of a particular good, service or experience. In some examples, the instrument may have multiple values, such as accepted value, a promotional value and/or a residual value. For example, using the aforementioned restaurant as the example provider, an electronic indication in a mobile application that shows $50 of value to be used as payment for a meal check at the restaurant. In some examples, the accepted value of the instrument is defined by the value exchanged for the instrument. In some examples, the promotional value is defined by the promotion from which the instrument resulted and is the value of the instrument beyond the accepted value. In some examples, the residual value is the value after redemption, the value after the expiry or other violation of a redemption parameter, the return or exchange value of the instrument and/or the like.

As used herein, the term “redemption” refers to the use, exchange or other presentation of an instrument for at least a portion of a good, service or experience as defined by the instrument and its related promotion. In some examples, redemption includes the verification of validity of the instrument. In other example embodiments, redemption may include an indication that a particular instrument has been redeemed and thus no longer retains an actual, promotional and/or residual value (e.g., full redemption). In other example embodiments, redemption may include the redemption of at least a portion of its actual, promotional and/or residual value (e.g., partial redemption). An example of redemption, using the aforementioned restaurant as the example provider, is the exchange of the $50 instrument and $50 to settle a $100 meal check.

As used herein, the term “impression” refers to a metric for measuring how frequently consumers are provided with marketing information related to a particular good, service, or promotion. Impressions may be measured in various different manners, including, but not limited to, measuring the frequency with which content is served to a consumer (e.g., the number of times images, websites, or the like are requested by consumers), measuring the frequency with which electronic marketing communications including particular content are sent to consumers (e.g., a number of e-mails sent to consumers or number of e-mails including particular promotion content), measuring the frequency with which electronic marketing communications are received by consumers (e.g., a number of times a particular e-mail is read), or the like. Impressions may be provided through various forms of media, including but not limited to communications, displays, or other perceived indications, such as e-mails, text messages, application alerts, mobile applications, other type of electronic interface or distribution channel and/or the like, of one or more promotions.

As used herein, the term “electronic marketing information” refers to various electronic data and signals that may be interpreted by a promotion and marketing service to provide improved electronic marketing communications. Electronic marketing information may include, without limitation, clickstream data (defined below), transaction data (defined below), location data (defined below), communication channel data (defined below), discretionary data (defined below), or any other data stored by or received by the promotion and marketing service for use in providing electronic communications to consumers.

As used herein, the term “clickstream data” refers to electronic information indicating content viewed, accessed, edited, or retrieved by consumers. This information may be electronically processed and analyzed by a promotion and marketing service to improve the quality of electronic marketing and commerce transactions offered by, through, and in conjunction with the promotion and marketing service. It should be understood that the term “clickstream” is not intended to be limited to mouse clicks. For example, the clickstream data may include various other consumer interactions, including without limitation, mouse-over events and durations, the amount of time spent by the consumer viewing particular content, the rate at which impressions of particular content result in sales associated with that content, demographic information associated with each particular consumer, data indicating other content accessed by the consumer (e.g., browser cookie data), the time or date on which content was accessed, the frequency of impressions for particular content, associations between particular consumers or consumer demographics and particular impressions, and/or the like.

As used herein, the term “transaction data” refers to electronic information indicating that a transaction is occurring or has occurred via the system. Transaction data may also include information relating to the transaction. For example, transaction data may include a timestamp, consumer payment or billing information, consumer shipping information, items purchased by the consumer, a merchant rewards account number associated with the consumer, the type of shipping selected by the consumer for fulfillment of the transaction, or the like.

As used herein, the term “location data” refers to electronic information indicating a particular location. Location data may be associated with a network asset requester (e.g., consumer), a network asset provider (e.g., merchant), or any other entity capable of interaction with the promotion and marketing service. For example, in some embodiments location data is provided by a location services module of a network asset requester device. In some embodiments, location data may be provided by a network asset provider indicating the location of network asset requesters within their retail location. In some embodiments, location data may be provided by network asset providers to indicate the current location of the network asset provider (e.g., a food truck or delivery service). It should be appreciated that location data may be provided by various systems capable of determining location information, including, but not limited to, global positioning service receivers, indoor navigation systems, cellular tower triangulation techniques, video surveillance systems, or radio frequency identification (RFID) location systems. Throughout this specification, the terms “user device,” “network asset requester device,” and “consumer device” may be used interchangeably.

As used herein, the term “communication channel data” refers to electronic information relating to the particular device or communication channel upon which a merchant or consumer communicates with the promotion and marketing service. In this regard, communication channel data may include the type of device used by the consumer or merchant (e.g., smart phone, desktop computer, laptop, netbook, tablet computer), the Internet Protocol (IP) address of the device, the available bandwidth of a connection, login credentials used to access the channel (e.g., a user account and/or password for accessing the promotion and marketing service), or any other data pertaining to the communication channel between the promotion and marketing service and an entity external to the promotion and marketing service.

As used herein, the term “discretionary data” refers to electronic information provided by a merchant or consumer explicitly to the promotion and marketing service in support of improved interaction with the promotion and marketing service. Upon registering with the promotion and marketing service or at any time thereafter, the consumer or merchant may be invited to provide information that aids the promotion and marketing service in providing services that are targeted to the particular needs of the consumer or merchant. For example, a consumer may indicate interests, hobbies, their age, gender, or location when creating a new account. A merchant may indicate the type of goods or services provided, their retail storefront location, contact information, hours of operation, or the like.

It should be appreciated that the term “discretionary data” is intended to refer to information voluntarily and explicitly provided to the promotion and marketing service, such as by completing a form or survey on a website or application hosted by the promotion and marketing service. However, it should be appreciated that the examples of discretionary data provided above may also be determined implicitly or through review or analysis of other electronic marketing information provided to the promotion and marketing service. It should also be appreciated that the promotion and marketing service may also grant access to certain features or tools based on whether certain discretionary data has been provided. For example, the consumer may be required to provide information relating to their interests or location during a registration process.

As used herein, the term “offering parameters” refers to terms and conditions under which the promotion is offered by a promotion and marketing service to consumers. These offering parameters may include parameters, bounds, considerations and/or the like that outline or otherwise define the terms, timing, constraints, limitations, rules or the like under which the promotion is sold, offered, marketed, or otherwise provided to consumers. Example offering parameters include, using the aforementioned restaurant as the example provider, limited to one instrument per person, total of 100 instruments to be issued, a run duration of when the promotion will be marketed via the promotion and marketing service, and parameters for identifying consumers to be offered the promotion (e.g., factors influencing how consumer locations are used to offer a promotion).

As used herein, the term “redemption parameters” refers to terms and conditions for redeeming or otherwise obtaining the benefit of promotions obtained from a promotion and marketing service. The redemption parameters may include parameters, bounds, considerations and/or the like that outline the term, timing, constraints, limitations, rules or the like for how and/or when an instrument may be redeemed. For example, the redemption parameters may include an indication that the instrument must be redeemed prior to a specified deadline, for a specific good, service or experience and/or the like. For example, using the aforementioned restaurant as the example provider, the redemption parameters may specify a limit of one instrument per visit, that the promotion must be used in-store only, or that the promotion must be used by a certain date.

As used herein, the term “promotion content” refers to display factors or features that influence how the promotion is displayed to consumers. For example, promotion content may include an image associated with the promotion, a narrative description of the promotion or the merchant, a display template for association with the promotion, or the like. For example, merchant self-service indicators (defined below) may be used to identify promotion offers that were generated by merchants with similar characteristics to the merchant self-service indicators. Various other factors may be used to generate the promotion offer, such as the success of the promotion offers generated by the merchants with similar characteristics, the product availability of the merchant, and the like.

As used herein, the term “promotion component” is used to refer to elements of a particular promotion that may be selected during a promotion generation process. Promotion components may include any aspect of a promotion, including, but not necessarily limited to, offering parameters, redemption parameters, and promotion content. For example, promotion components may include, but are not limited to, promotion titles, promotion ledes (e.g., a short text phrase displayed under a promotion title), promotion images, promotion prices, promotion discount levels, promotion style sheets, promotion fonts, promotion e-mail subjects, promotion quantities, promotion fine print options, promotion fees assessed to the merchant by the promotion and marketing service, or the like. Promotion components may also include various flags and settings associated with registration and verification functions for a merchant offering the promotion, such as whether the identity of the merchant has been verified, whether the merchant is registered with the promotion and marketing service, or the like.

As used herein, the term “electronic marketing communication” refers to any electronically generated information content provided by the promotion and marketing service to a consumer for the purpose of marketing a promotion, good, or service to the consumer. Electronic marketing communications may include any email, short message service (SMS) message, web page, application interface, or the like, electronically generated for the purpose of attempting to sell or raise awareness of a product, service, promotion, or merchant to the consumer.

It should be appreciated that the term “electronic marketing communication” implies and requires some portion of the content of the communication to be generated via an electronic process. For example, a telephone call made from an employee of the promotion and marketing service to a consumer for the purpose of selling a product or service would not qualify as an electronic marketing communication, even if the identity of the call recipient was selected by an electronic process and the call was dialed electronically, as the content of the telephone call is not generated in an electronic manner. However, a so-called “robo-call” with content programmatically selected, generated, or recorded via an electronic process and initiated by an electronic system to notify a consumer of a particular product, service, or promotion would qualify as an electronic marketing communication. Similarly, a manually drafted e-mail sent from an employee of the promotion and marketing service to a consumer for the purpose of marketing a product would not qualify as an electronic marketing communication. However, a programmatically generated email including marketing materials programmatically selected based on electronic marketing information associated with the recipient would qualify as an electronic marketing communication.

As used herein, the term “business analytic data” refers to data generated by the promotion and marketing service based on electronic marketing information to assist with the operation of the promotion and marketing service and/or one or more merchants. The various streams of electronic marketing information provided to and by the promotion and marketing service allow for the use of sophisticated data analysis techniques that may be employed to identify correlations, relationships, and other associations among elements of electronic marketing information. These associations may be processed and formatted by the promotion and marketing service to provide reports, recommendations, and services both internal to the promotion and marketing service and to merchants in order to improve the process by which merchants and promotion and marketing service engage with consumers. For example, the promotion and marketing service may analyze the electronic marketing information to identify an increased demand for a particular product or service, and provide an electronic report to a merchant suggesting the merchant offer the particular product or service. Alternatively, the promotion and marketing service may identify that a particular product or service is not selling well or that sales of the product or service result in the merchant losing money, customers, or market share (e.g., after consumers order a particular menu item, they never come back to the merchant), and suggest that the merchant should discontinue offering that product or service.

It should be appreciated that the term “business analytic data” is intended to refer to electronically and programmatically generated data. For example, a printed report or letter manually drafted by an employee of the promotion and marketing service would not be said to include business analytic data, even if said data was used by the employee during the drafting process, while a data disk or downloaded file containing analytics generated by the promotion and marketing service would be considered business analytic data.

As used herein, the terms “merchant self-service indicator” and “promotion context” relate to data associated with the merchant that may be used to classify the merchant or suggest promotion components to the merchant. A promotion context may include a plurality of merchant self-service indicators. For example, a promotion context may include multiple merchant self-service indicators that describe various features or characteristics of the merchant, such as a the type of industry of the merchant, the type of products or services sold by the merchant, the size of the merchant, the location of the merchant, the sales volume of the merchant, reviews and ratings for the merchant, or the like.

In some embodiments, the merchant self-service indicators are a result of analytics that allow for generation of promotions that are ideal for the particular merchant's circumstances. For example, the merchant self-service indicators may be used to identify optimal promotions for the particular merchant based on their exact location (e.g., the particular city street of the merchant as opposed to a wider range, such as a zip code), the merchant's exact products and services offered (e.g., pizzerias that only serve deep dish pizza, restaurants that become nightclubs after 11:00 pm), the merchant's price point (e.g., barbershops that charge more than $20 for a haircut), or the date or season of the year (e.g., offering ski equipment during the winter, or holiday themed promotions during the holiday season), or the like. These merchant self-service indicators may be used in a self-service process to identify promotion components that were used by other merchants that share one or more same or similar merchant self-service indicators. For example, after initial registration and verification, the promotion and marketing service may identify the merchant self-service indicators associated with the newly registered merchant, such as by looking up the merchant in a merchant database or by receiving the merchant self-service indicators directly from the merchant (e.g., by a fillable form). The merchant self-service indicators and promotion contexts may be used for refund prediction. For example, such attributes may be used to identify weather a promotion for a specific merchant is likely to satisfy consumers (e.g., the promotion has 70% chance to satisfy consumers and therefore has 30% chance of resulting in refund requests). It should be appreciated that the term “programmatically expected” indicates machine prediction of occurrence of certain events. For example, a “programmatically expected” number of refund requests is a number determined by machine prediction specifying the expected number of promotion purchases that will result in refund requests.

As used herein, the term “likelihood” refers to a measure of probability for occurrence of a particular event. For example, the likelihood that a customer is satisfied with a promotion may be a value associated with a specific scale. In some implementations, the machine predictions discussed above are based, at least in part, on the “likelihood” that an event will occur. Similarly, in some implementations, machine predictions are based on attributes associated with a merchant and an associated merchant promotion.

It should be appreciated that the terms “refund,” “return,” and “transaction termination” and “termination transaction” imply canceling/reversal of a transaction associated with a device rendered object. For example, a device terminating, returning, and/or requesting a refund for a transaction may be described by the act of returning goods or services received while requesting return of a purchase price for the transaction.

The term “transaction data” refers to electronic information indicating that a transaction is occurring or has occurred via the system. Transaction data may also include information relating to the transaction. For example, transaction data may include a timestamp, consumer payment or billing information, consumer shipping information, items purchased by the consumer, a merchant rewards account number associated with the consumer, the type of shipping selected by the consumer for fulfillment of the transaction, or the like. In embodiments, a transaction may be completed by a network asset requesting device and the system when the network asset requesting device interacts with a device rendered object in such a way that a purchase transaction is completed. In embodiments, a transaction may be completed by a network asset requesting device and the system when the network asset requesting device interacts with a device rendered object in such a way that a termination transaction is completed.

The term “timestamp” refers to a sequence of characters or encoded information identifying when a certain event occurred according to network time, usually giving date and time of day, sometimes accurate to a small fraction of a second.

The term “system transaction data” refers to a system wide aggregation of transaction data related to all transactions occurring between network asset requester devices, network asset provider devices, and device rendered objects. The term “system transaction count” refers to a number of transactions that have occurred system wide according to the system transaction data. In some embodiments, the system transaction data comprises a volume of currency associated with transactions indicating purchases of device rendered objects (e.g., promotions).

The term “network time interval” refers to a duration of network time defined by a starting timestamp and an ending timestamp, where the ending timestamp occurs subsequent to the starting timestamp. A network time interval may be from a past duration of time, a current duration of time, or a future duration of time. Examples of network time intervals may include one hour, one day, one week, one month, one year, and the like.

The term “system resource allocation” refers to an aggregation of network assets that is allocated to be available for fulfillment of network asset requests.

The term “system resource allocation threshold” refers to a required amount of system resources that need to be available in order to fulfill network asset requests.

The term “prediction value” refers to a programmatically generated likelihood of an event occurring. In embodiments, the prediction value is generated using machine learning.

The term “historical data” refers to any data associated with timestamps occurring prior to a defined timestamp or within a particular network time period.

It will be appreciated that network assets, device rendered objects, network asset providers, network asset requesters, and the like, as described herein, may have associated therewith one or more attributes.

It should be understood that each of the attributes discussed in this application, may be in some embodiments, may be a primary or a secondary attribute. A list of exemplary attributes is provided below.

In some implementations, one attribute may represent category data, specifically beauty, wellness and healthcare. To determine a normalized value of the one attribute, an algorithm may be executed on associated raw data related to a transaction. For example, if the category data associated with a promotion transaction is “beauty, wellness and healthcare,” the value of the one attribute is 1. If the category data associated with a transaction is not “beauty, wellness and healthcare,” the value of the one attribute is 0.

In some embodiments, a number of example attributes relate to category data and sub-category data. There is also a number of attributes related to location data. It should be understood that attribute data related to location and hyper location data may be generated in a similar fashion. For example, if the location data associated with a transaction is “Chicago,” the value of a corresponding attribute may be 1. If the category data associated with a transaction is not “Chicago,” the value of the corresponding attribute may be 0.

It should also be understood that transactions may have associated data indicating one or more categories, sub-categories, location, hyper-locations, prices or the like. For example, a transaction may be associated with a gym, and the gym may be associated with category data such as “beauty, wellness, and healthcare,” “Food and drink,” “Leisure Offers and Activities” and/or “Services.” A gym may also have more than one location, and may be able to provide promotions in a variety of price ranges and time frames.

Example attribute data can also be associated with review websites such as Yelp®, Google®, Yahoo®, City Search®, Trip Advisor®. It should be understood that any review website could have associated attribute data, such as for example Zagat®, Bing® or the like. It should also be understood that attribute data associated with reviews related to one or more categories may be generated. For example, a website may provide reviews related to a provider's food, service, décor, price or the like. Attribute data may be generated related to each of one or more categories, such as a provider's food, service, décor, price, or the like.

It should also be understood that a location, hyper-location, category or sub-category may affect data available for the provider of a transaction. For example, promotion transactions purchased from providers from different locations (e.g., different countries, states, neighborhoods or the like) may be associated with different attribute data. For example, different countries have different credit reporting rules and agencies. Thus, a system may utilize a first combination of attributes for a transaction from a provider in a first location, hyper-location, category or sub-category and a second combination of attributes for a transaction from provider in a second location, hyper-location, category or sub-category.

In one implementation, other attribute data may be used. For example, attribute “bad month” may relate to identifying transactions having attributes associated with network time intervals (e.g., booking months) where prior transactions have involved products, services, and/or other offerings in one or more categories categorized as having high termination transaction rates based on prior performance data. The feature may be normalized such that if the sub-category of the promotion transaction is associated with high return rates, the attribute is 1, else the attribute is 0. Other example attributes are “bad market,” which may be normalized such that if the transaction has an attribute associated with GPS coordinates that indicate a significant distance requiring travel to a location and/or hyper local region associated with high return rates, the attribute is 1, else the attribute is 0. Another example feature is “average price for sub-category.” In some embodiments, GPS coordinates are used as an attribute to associate a merchant with a merchant division, which is similar to a neighborhood or city.

Similar attributes may be clustered, grouped, or aggregated. For example, attributes associated with locations or location based attributes may be grouped under header attribute “location.” For example, a division attributes specifying a division where the promotion is offered and an attribute specifying a distance from a center of a city where a promotion is offered may be clustered under the location header attribute. Similarly, attributes associated with “past performance,” “category & service,” “completion,” “maximum capacity,” “hero score,” “review data” may each also be clustered and/or grouped under header attributes. For example, with respect to promotion transaction associated with a merchant providing a service, attributes specifying past performance data can be for (1) the same merchant and the same service, (2) only the same merchant, (3) only the same service may be clustered under attribute header “past performance.”

Table A shows example attributes.

TABLE A Type Features Location division, distance to city, etc. past performance same merchant & service, same service, same merchant, etc. category & service service header, primary deal service, etc. booking month holiday, pre-holiday, etc. maximum capacity units_avail, etc. hero score predicted 30 day bookings, predicted 60 day bookings, etc. review data yelp_n_review, yelp_rating, yelp_avil, google_n_review, facebook_fans, etc.

The clustered or the non-clustered attributes may be used to train a machine learning model. It should be understood that the selection of attributes or clusters of attributes for training machine learning models or for promotion termination prediction processes can greatly affect the respective performance. In some implementations, attributes and/or clusters of attributes are selected based on statistical analysis. In some implementations, selection of the most significant attributes is based on one or more different attribute selection approaches. These approaches may be (1) forward selection, which is starting with the most significant attributes and incrementally adding a next significant attribute until the model is stable; (2) backward elimination, which starts with all the attributes and exclude the non-significant attributes one by one until the model is stable; (3) a combination of forward selection and backward elimination; and (4) checking the significance of the attribute by statistical model (regression). In one embodiment, each attribute selection approach may give a subset of significant attributes. The attributes that are not shown to be significant by one or more of the attribute selection approaches may be excluded from the model.

In some implementations, the processes disclosed herein are performed according to a random forest model. The model may operate by constructing multiple decision trees at training. Each decision tree may be based on different attributes. In some implementations, the random forest model output is the mode of classes or the most occurring class among all the trees of the random forest. In some implementations, the random forest model is trained with historical data associated with various attributes. In some implementations, different trained models may be utilized for different locations and/or types of promotion transactions.

Technical Underpinnings and Implementation of Exemplary Embodiments

Merchants, including manufacturers, wholesalers, and retailers, have spent a tremendous amount of time, money, manpower, and other resources to determine the best way to market their products to consumers. Whether a given marketing effort is successful is often determined based on the return-on-investment offered to the merchant from increased awareness, sales, and the like, of the merchant's goods and services in exchange for the resources spent on the marketing effort. In other words, optimal marketing techniques generally maximize the benefit to the merchant's bottom line while minimizing the cost spent on marketing. To this end, a merchant's marketing budget may be spent in a variety of different manners including advertising, offering of discounts, conducting market research, and various other known marketing techniques. The end goal of these activities is to ensure that products are presented to consumers in a manner that maximizes the likelihood that the consumers will purchase the product from the merchant that performed the marketing activities while minimizing the expense of the marketing effort.

The advent of electronic commerce has revolutionized the marketing process. While merchants would typically have to perform costly market research such as focus groups, surveys, and the like to obtain detailed information on consumer preferences and demographics, the digital age has provided a wealth of new consumer information that may be used to optimize the marketing and sales process. As a result, new technologies have been developed to gather, aggregate, analyze, and report information from a variety of electronic sources.

So-called “clickstream data” provides a robust set of information describing the various interactions consumers have with electronic marketing information provided to them by merchants and others. Promotion and marketing services have been developed with sophisticated technology to receive and process this data for the benefit of both merchants and consumers. These services assist merchants with marketing their products to interested consumers, while reducing the chance that a consumer will be presented with marketing information in which the consumer has no interest. Some promotion and marketing services further leverage their access to the trove of electronic marketing information to assist merchants and consumers with other tasks, such as offering improved merchant point-of-sale systems, improved inventory and supply chain management, improved methods for delivering products and services, and the like.

Unlike conventional marketing techniques related to the use of paper or other physical media (e.g., coupons clipped from a weekly newspaper), promotion and marketing services offer a wealth of additional electronic solutions to improve the experience for consumers and merchants. The ability to closely monitor user impressions provides the ability for the promotion and marketing service to gather data related to the time, place, and manner in which the consumer engaged with the impression (e.g., viewed, clicked, moused-over) and obtained and redeemed the promotion. The promotion and marketing service may use this information to determine which products and services are most relevant to the consumer's interest, and to provide marketing materials related to said products and services to the consumer, thus improving the quality of the electronic marketing communications received by the consumer. Merchants may be provided with the ability to dynamically monitor and adjust the parameters of promotions offered by the promotion and marketing service, ensuring that the merchant receives a positive return on their investment. For example, the merchant can closely monitor the type, discount level, and quantity sold of a particular promotion on the fly, while with traditional printed coupons the merchant would not be able to make any changes to the promotion after the coupon has gone to print. Each of these advancements in digital market and promotion distribution involve problems unique to the digital environment not before seen in traditional print or television broadcast marketing.

However, these promotion and marketing services are not without problems. Although the clickstream data provides a wealth of information, the inventors have determined that existing techniques may not always leverage this information in an efficient or accurate manner. Technology continues to rapidly advance in the field of analytics and the processing of this information, offering improved data gathering and analysis techniques, resulting in more relevant and accurate results provided in a more efficient manner. Electronic marketing services continue to evolve and provide improved methods for engaging consumers and spreading awareness of products offered by promotion and marketing services.

In many cases, the inventors have determined that these services are constrained by technological obstacles unique to the electronic nature of the services provided, such as constraints on data storage, accuracy of data available, machine communication and processor resources. The inventors have identified that the wealth of electronic data available to these services and the robust nature of electronic marketing communications techniques present new challenges never contemplated in the world of paper coupons and physical marketing techniques. The inventors have further determined that even technological methods that leverage computers for statistical analysis and consumer behavior modeling (e.g., television rating systems) fail to address problems associated with providing relevant, high quality electronic marketing communications (e.g., impressions) to consumers in a manner that maximizes accuracy, minimizes error, is user friendly and provides for efficient allocation of resources. Embodiments of the present invention as described herein serve to correct these errors and offer improved resource utilization, thus providing improvements to electronic marketing services that address problems arising out of the electronic nature of those services.

System Architecture and Example Apparatus

Methods, apparatuses, and computer program products of the present invention may be embodied by any of a variety of devices. For example, the method, apparatus, and computer program product of an example embodiment may be embodied by a networked device, such as a server or other network entity, configured to communicate with one or more devices, such as one or more client devices. Additionally or alternatively, the computing device may include fixed computing devices, such as a personal computer or a computer workstation. Still further, example embodiments may be embodied by any of a variety of mobile terminals, such as a portable digital assistant (PDA), mobile telephone, smartphone, laptop computer, tablet computer, or any combination of the aforementioned devices.

In this regard, FIG. 1 discloses an example computing system within which embodiments of the present invention may operate. Network asset requester devices and network asset provider devices may access a resource management 102 via a network 112 (e.g., the Internet, or the like) using computer devices 108A through 108N and 110A through 110N, respectively (e.g., one or more network asset requester devices 108A-108N or one or more network asset provider devices 110A-110N). Moreover, the resource management system 102 may comprise a server 104 in communication with a database 106.

The server 104 may be embodied as a computer or computers as known in the art. The server 104 may provide for receiving of electronic data from various sources, including but not necessarily limited to the network asset requester devices 108A-108N and the network asset provider devices 110A-110N. For example, the server 104 may be operable to receive and process clickstream data provided by the network asset requester devices 108 and/or the network asset provider devices 110. The server 104 may also facilitate e-commerce transactions based on transaction information provided by the network asset requester devices 108 and/or the network asset provider devices 110. The server 104 may facilitate the generation and providing of various electronic communications and device rendered objects based on the received electronic data.

The database 106 may be embodied as a data storage device such as a Network Attached Storage (NAS) device or devices, or as a separate database server or servers. The database 106 includes information accessed and stored by the server 104 to facilitate the operations of the resource management system 102. For example, the database 106 may include, without limitation, user account credentials for system administrators, network asset providers (e.g., merchants), and network asset requesters (e.g., consumers), data indicating the device rendered objects transmittable by the resource management system, clickstream data, analytic results, reports, financial data, and/or the like.

The network asset requester devices 108A-108N may be any computing device as known in the art and operated by a network asset requester (e.g., consumer). Electronic data received by the server 104 from the network asset requester devices 108A-108N may be provided in various forms and via various methods. For example, the network asset requester devices 108A-108N may include desktop computers, laptop computers, smartphones, netbooks, tablet computers, wearables, and the like. The information may be provided through various sources on these consumer devices.

In embodiments where a network asset requester device 108 is a mobile device, such as a smart phone or tablet, the network asset requester device 108 may execute an “app” to interact with the resource management system 102. Such apps are typically designed to execute on mobile devices, such as tablets or smartphones. For example, an app may be provided that executes on mobile device operating systems such as Apple Inc.'s iOS®, Google Inc.'s Android®, or Microsoft Inc.'s Windows 8®. These platforms typically provide frameworks that allow apps to communicate with one another and with particular hardware and software components of mobile devices. For example, the mobile operating systems named above each provide frameworks for interacting with location services circuitry, wired and wireless network interfaces, user contacts, and other applications in a manner that allows for improved interactions between apps while also preserving the privacy and security of consumers. In some embodiments, a mobile operating system may also provide for improved communication interfaces for interacting with external devices (e.g., home automation systems, indoor navigation systems, and the like). Communication with hardware and software modules executing outside of the app is typically provided via application programming interfaces (APIs) provided by the mobile device operating system.

The resource management system 102 may leverage the application framework offered by the mobile operating system to allow network asset requesters (e.g., consumers) to designate which information is provided to the app and which may then be provided to the resource management system 102. In some embodiments, network asset requesters may “opt in” to provide particular data to the resource management system 102 in exchange for a benefit, such as improved relevancy of communications transmitted to the network asset requester device. In some embodiments, the network asset requester device may be provided with privacy information and other terms and conditions related to the information provided to the resource management system 102 during installation or use of the app. Once the network asset requester provides access to a particular feature of the mobile device, information derived from that feature may be provided to the resource management system 102 to improve the quality of the network asset requester's interactions with the resource management system 102.

For example, the network asset requester may indicate that they wish to provide location information to the app from location services circuitry included in their mobile device. Providing this information to the resource management system 102 may enable the resource management system 102 to transmit instructs for rendering device rendered objects that display promotions to the network asset requester device that are relevant to the particular location, e.g., GPS coordinates, of the network asset requester device (e.g., by providing device rendered objects for displaying promotions for network asset providers proximate to the network asset requester device's current location). It should be appreciated that the various mobile device operating systems may provide the ability to regulate the information provided to the app associated with the resource management system 102. For example, the network asset requester may decide at a later point to disable the ability of the app to access the location services circuitry, thus limiting the access of the network asset requester device's location information to the resource management system 102.

Additionally or alternatively, the network asset requester device 108 may interact through the resource management system 102 via a web browser. As yet another example, the network asset requester device 108 may include various hardware or firmware designed to interface with the resource management system 102 (e.g., where the network asset requester device 108 is a purpose-built device offered for the primary purpose of communicating with the resource management system 102, such as a kiosk).

The network asset provider devices 110A-110N may be any computing device as known in the art and operated by a network asset provider. For example, the network asset provider devices 110A-110N may include a network asset provider point-of-sale, a network asset provider e-commerce server, a network asset provider inventory system, or a computing device accessing a web site designed to provide network asset provider access (e.g., by accessing a web page via a browser using a set of network asset provider account credentials). Electronic data received by the resource management system 102 from the network asset provider devices 110A-110N may also be provided in various forms and via various methods. For example, the network asset provider devices 110A-110N may provide real-time transaction and/or inventory information as transactions occur with the network asset provider. In other embodiments, the network asset provider devices 110A-110N may be employed to provide information to the resource management system 102 to enable the resource management system 102 to generate instructions for device rendered objects renderable to display information (e.g., promotions or other marketing information) to be transmitted to network asset requester devices.

An example of a data flow for exchanging electronic information among one or more network asset provider devices, network asset provider devices, and the resource management system is described below with respect to FIG. 3.

Example Apparatus For Implementing Embodiments of the Present Invention

The server 104 may be embodied by one or more computing systems, such as apparatus 200 shown in FIG. 2. As illustrated in FIG. 2, the apparatus 200 may include a processor 202, a memory 204, input/output circuitry 206, communications circuitry 208, resource allocation calculation circuitry 210, termination transaction termination prediction circuitry 212, and termination rate calculation circuitry 214. The apparatus 200 may be configured to execute the operations described above with respect to FIG. 1 and below with respect to FIGS. 3-6. Although these components 202-214 are described with respect to functional limitations, it should be understood that the particular implementations necessarily include the use of particular hardware. It should also be understood that certain of these components 202-214 may include similar or common hardware. For example, two sets of circuitry may both leverage use of the same processor, network interface, storage medium, or the like to perform their associated functions, such that duplicate hardware is not required for each set of circuitry. The use of the term “circuitry” as used herein with respect to components of the apparatus should therefore be understood to include particular hardware configured to perform the functions associated with the particular circuitry as described herein.

The term “circuitry” should be understood broadly to include hardware and, in some embodiments, software for configuring the hardware. For example, in some embodiments, “circuitry” may include processing circuitry, storage media, network interfaces, input/output devices, and the like. In some embodiments, other elements of the apparatus 200 may provide or supplement the functionality of particular circuitry. For example, the processor 202 may provide processing functionality, the memory 204 may provide storage functionality, the communications circuitry 208 may provide network interface functionality, and the like.

In some embodiments, the processor 202 (and/or co-processor or any other processing circuitry assisting or otherwise associated with the processor) may be in communication with the memory 204 via a bus for passing information among components of the apparatus. The memory 204 may be non-transitory and may include, for example, one or more volatile and/or non-volatile memories. In other words, for example, the memory may be an electronic storage device (e.g., a computer readable storage medium). The memory 204 may be configured to store information, data, content, applications, instructions, or the like, for enabling the apparatus to carry out various functions in accordance with example embodiments of the present invention.

The processor 202 may be embodied in a number of different ways and may, for example, include one or more processing devices configured to perform independently. Additionally or alternatively, the processor may include one or more processors configured in tandem via a bus to enable independent execution of instructions, pipelining, and/or multithreading. The use of the term “processing circuitry” may be understood to include a single core processor, a multi-core processor, multiple processors internal to the apparatus, and/or remote or “cloud” processors.

In an example embodiment, the processor 202 may be configured to execute instructions stored in the memory 204 or otherwise accessible to the processor. Alternatively, or additionally, the processor may be configured to execute hard-coded functionality. As such, whether configured by hardware or software methods, or by a combination thereof, the processor may represent an entity (e.g., physically embodied in circuitry) capable of performing operations according to an embodiment of the present invention while configured accordingly. Alternatively, as another example, when the processor is embodied as an executor of software instructions, the instructions may specifically configure the processor to perform the algorithms and/or operations described herein when the instructions are executed.

In some embodiments, the apparatus 200 may include input/output circuitry 206 that may, in turn, be in communication with processor 202 to provide output to the user and, in some embodiments, to receive an indication of a user input. The input/output circuitry 206 may comprise a user interface and may include a display and may comprise a web user interface, a mobile application, a client device, a kiosk, or the like. In some embodiments, the input/output circuitry 206 may also include a keyboard, a mouse, a joystick, a touch screen, touch areas, soft keys, a microphone, a speaker, or other input/output mechanisms. The processor and/or user interface circuitry comprising the processor may be configured to control one or more functions of one or more user interface elements through computer program instructions (e.g., software and/or firmware) stored on a memory accessible to the processor (e.g., memory 204, and/or the like).

The communications circuitry 208 may be any means such as a device or circuitry embodied in either hardware or a combination of hardware and software that is configured to receive and/or transmit data from/to a network and/or any other device, circuitry, or module in communication with the apparatus 200. In this regard, the communications circuitry 208 may include, for example, a network interface for enabling communications with a wired or wireless communication network. For example, the communications circuitry 208 may include one or more network interface cards, antennae, buses, switches, routers, modems, and supporting hardware and/or software, or any other device suitable for enabling communications via a network. Additionally or alternatively, the communication interface may include the circuitry for interacting with the antenna(s) to cause transmission of signals via the antenna(s) or to handle receipt of signals received via the antenna(s).

Resource allocation calculation circuitry 210 includes hardware configured to identify and determine a recommended system resource allocation threshold. The resource allocation calculation circuitry 210 may utilize processing circuitry, such as the processor 202, to perform these actions. The resource allocation calculation circuitry 210 may receive data from termination transaction prediction circuitry 212. In some implementations, the received data may be a normalized score indicative of a probability that a transaction will result in a termination transaction. For example, a termination transaction may be a request for return of merchandise accompanied by a request for a refund. However, it should also be appreciated that, in some embodiments, the resource allocation calculation circuitry 210 may include a separate processor, specially configured field programmable gate array (FPGA), or application specific interface circuit (ASIC) to classify, update reserve calculations, and train and use a machine learning model for reserve calculations. In some implementations, promotion transaction termination prediction circuitry 212, described below, may be sub-circuitry belonging to reserve calculation circuitry 210. The resource allocation calculation circuitry 210 may be implemented using hardware components of the apparatus configured by either hardware or software for implementing these planned functions.

Termination transaction prediction circuitry 212 includes hardware configured to identify and determine a prediction that a termination transaction associated with a device rendered object will occur, in a future network time period, subsequent to a first transaction associated with the device rendered object. In some implementations, the prediction is specified as a probability or likelihood that a promotion represented by the device rendered object will be terminated (i.e., a termination transaction will occur) in the future network period. The termination transaction prediction circuitry 212 may utilize processing circuitry, such as the processor 202, to perform these actions. However, it should also be appreciated that, in some embodiments, the termination transaction prediction circuitry 212 may include a separate processor, specially configured field programmable gate array (FPGA), or application specific interface circuit (ASIC) for determining a prediction specifying a likelihood that a transaction will be followed by an associated termination transaction. Similarly, termination rate calculation circuitry 214 includes hardware configured to identify and determine a historical rate of termination transaction for a given period of network time. Such prediction may also be specified as a numerical value. Again, it should also be appreciated that, in some embodiments, the termination rate calculation circuitry 214 may include a separate processor, specially configured field programmable gate array (FPGA), or application specific interface circuit (ASIC) for calculating a historical termination rate. Circuitry 212 and 214 may be implemented using hardware components of the apparatus configured by either hardware or software for implementing these planned functions.

As will be appreciated, any such computer program instructions and/or other type of code may be loaded onto a computer, processor or other programmable apparatus's circuitry to produce a machine, such that the computer, processor or other programmable circuitry that execute the code on the machine create the means for implementing various functions, including those described herein.

It is also noted that all or some of the information presented by the example displays discussed herein can be based on data that is received, generated and/or maintained by one or more components of apparatus 200. In some embodiments, one or more external systems (such as a remote cloud computing and/or data storage system) may also be leveraged to provide at least some of the functionality discussed herein.

As described above and as will be appreciated based on this disclosure, embodiments of the present invention may be configured as methods, mobile devices, backend network devices, and the like. Accordingly, embodiments may comprise various means including entirely of hardware or any combination of software and hardware. Furthermore, embodiments may take the form of a computer program product on at least one non-transitory computer-readable storage medium having computer-readable program instructions (e.g., computer software) embodied in the storage medium. Any suitable computer-readable storage medium may be utilized including non-transitory hard disks, CD-ROMs, flash memory, optical storage devices, or magnetic storage devices.

Example Resource Management System Interaction Data Flow

FIG. 3 depicts an example data flow 300 illustrating interactions between a server 302, one or more network asset requester devices 304, and one or more network asset provider devices 306. The server 302 may be implemented in the same or a similar fashion as the server 104 as described above with respect to FIG. 1, the one or more network asset requester devices 304 may be implemented in the same or a similar fashion as the network asset requester devices 108A-108N as described above with respect to FIG. 1, and the one or more network asset provider devices 306 may be implemented in the same or a similar fashion as the network asset provider devices 110A-110N as described above with respect to FIG. 1.

The data flow 300 illustrates how electronic information may be passed among various systems when employing a server 302 in accordance with embodiments of the present invention. The one or more network asset requester devices 304 and/or one or more network asset provider devices 306 may provide a variety of electronic marketing information to the server 302 for use in providing promotion and marketing services to the consumer. This electronic marketing information may include, but is not limited to, location data, clickstream data, transaction data, communication channel data, historical data, review data and/or discretionary data.

As a result of transactions performed between the one or more network asset requester devices 304 and the server 302, the server 302 may provide fulfillment data to the network asset requester devices. The fulfillment data may include information indicating whether the transaction was successful, the location and time the product will be provided to the network asset requester, instruments for redeeming promotions purchased by the network asset requester, or the like.

In addition to the e-commerce interactions with the one or more network asset requester devices 304 offered by the server 302, the server 302 may leverage information provided by the network asset requester devices to improve the relevancy of electronic communications to individual network asset requester or groups of network asset requester. In this manner, the server 302 may determine device rendered objects, promotions, goods, and services that are more likely to be of interest to a particular network asset requester or group of network asset requesters based on clickstream data, location data, and other information provided by and/or relating to particular network asset requesters. For example, the server 302 may detect the location of a network asset requester based on location data provided by the network asset requester device, and offer promotions based on the proximity of the network asset requester to the network asset provider associated with those promotions.

Alternatively, the server 302 may note that the network asset requester has an interest in a particular hobby (e.g., skiing) based on electronic marketing information associated with the network asset requester (e.g., a browser cookie that indicates they frequently visit websites that provide snowfall forecasts for particular ski resorts), and offer promotions associated with that hobby (e.g., a promotion offering discounted ski equipment rentals or lift tickets). It should be appreciated that a variety of different types of electronic marketing information could be provided to the server 302 for the purpose of improving the relevancy of marketing communications. It should also be appreciated that this electronic marketing information may be received from a variety of electronic sources, including various network asset requester devices, network asset provider devices, and other sources both internal and external to a promotion and marketing service. For example, other data sources may include imported contact databases maintained by merchants, electronic survey questions answered by consumers, and/or various other forms of electronic data.

It should also be appreciated that the server 302 may also control other factors of the electronic marketing communications sent to the consumer other than the particular promotions included in the electronic marketing communication. For example, the server 302 may determine the form, structure, frequency, and type of the electronic marketing communication. As with the content of the electronic marketing communication, these factors may be programmatically determined according to various methods, factors, and processes based on electronic data received by the server 302 for the purpose of maximizing the likelihood that the communication will be relevant to the recipient consumer.

The server 302 interactions with the one or more network asset provider devices 306 may be related to enabling the merchant to market their products using a promotion and marketing service. For example, the one or more network asset provider devices 306 may provide promotion data defining one or more promotions to be offered by the promotion and marketing service on behalf of the merchant. The server 302 may receive this information and generate information for providing such promotions via an e-commerce interface, making the promotions available for purchase by consumers. The server 302 may also receive information about products from the one or more network asset provider devices 306. For example, a merchant may provide electronic marketing information indicating particular products, product prices, inventory levels, and the like to be marketed via a promotion and marketing service. The server 302 may receive this information and generate listing information to offer the indicating products to consumers via a promotion and marketing service.

The one or more network asset provider devices 306 may also receive information from the server 302. For example, in some embodiments a merchant may obtain access to certain business analytic data aggregated, generated, or maintained by the server 302. As a particular example, a merchant might offer to pay for consumer demographic data related to products or services offered by the merchant. It should be appreciated, however, that a merchant may not need to list any products or services via the promotion and marketing service in order to obtain such data. For example, the promotion and marketing service may enable merchants to access electronic marketing data offered via the promotion and marketing service based on a subscription model. The one or more network asset provider devices 306 may also receive electronic compensation data from the server 302. For example, when a promotion or product is sold by the promotion and marketing service on behalf of the merchant, a portion of the received funds may be transmitted to the merchant. The compensation data may include information sufficient to notify the merchant that such funds are being or have been transmitted. In some embodiments, the compensation data may take the form of an electronic wire transfer directly to a merchant account. In some other embodiments, the compensation data may indicate that a promotion or product has been purchased, but the actual transfer of funds may occur at a later time. For example, in some embodiments, compensation data indicating the sale of a promotion may be provided immediately, but funds may not be transferred to the merchant until the promotion is redeemed by the consumer.

Embodiments advantageously provide for improvements to the server by allowing prediction of system resource volumes more efficiently and accurately. In turn, this reduces the server stress. For example, by eliminating unnecessary reuse of global variables throughout iterations, the server reduces the processing associated with predicting required system resource volumes in a given future network period. In turn, the processing power requirement of the server is significantly reduced.

Example Processes For System Resource Calculation

As described, a system may utilize network communications to deliver remote computing devices with device rendered objects representing available promotions related to products, services or experiences offered by providers that may be of interest.

In order to maintain accurate data stores associated with provider accounts, the system must have an available volume system resources. The system must also have an available volume system resources to maintain accurate data stores associated with consumer accounts.

Naturally, the ability to accurately predict required volumes of system resources can significantly impact server processing power and time. Accordingly, there exists a dire market need for methods and systems that can accurately predict system resource volumes that will result from termination transactions.

FIG. 4 is a flow chart of an example process 400 for predicting system resource allocation thresholds. The process 400 begins with receiving first transaction data and second transaction data, where the first transaction data comprises a first timestamp and the second transaction data comprises a second timestamp (402). In some implementations, the first and second transaction data are associated with a device rendered object of a plurality of device rendered objects. In some implementations, the second timestamp is subsequent the first timestamp. In some embodiments, the second transaction is a termination transaction. In some embodiments, the device rendered object is a set of instructions that, when executed by a consumer computing device, enables an electronic display interface that represents a promotion. In some implementations, the promotion may be for any goods offered by a department store. In some implementations, the promotion may be for a specific type of goods offered by the department store (e.g., camping equipment). In some implementations, the promotion may be for a specific item, such as, a bike. Similarly, the promotion may be for services offered by a service store, where the service store may request transmittal of promotion for services provided by the store (e.g., haircut, hair coloring, oil change). In some implementations, stores may offer a combination of services and goods.

The process 400 continues with receiving system transaction data (404). In some embodiments, system transaction data comprises a network time interval and a system transaction count occurring during the network time interval. In some embodiments, the network time interval is a calendar month, a year, two years, and the like. In some embodiments, the system transaction data comprises a volume of currency associated with transactions indicating purchases of device rendered objects (e.g., promotions).

Step 406, shown in phantom or dashed lines, is an optional step of process 400. The process 400 may continue with determining, for the first device rendered object, one or more first attributes, the first attributes being for determining one or more prediction values (408). In some implementations, one of the first attributes may be an annual season associated with a network time interval, or booking month, of the device rendered object. By way of further example, the attribute may be a value specifying difference in GPS coordinates associated with a center of a city where the device rendered object is redeemable. Other examples and implementations details for the second values will be discussed in more detail below.

The process 400 continues with determining, based on the first transaction data, the second transaction data, and the system transaction data, a first prediction value that indicates a programmatically expected number of transaction terminations for a future network time interval (408). For example, historical booking transaction data for previous network intervals are used along with a programmatically expected rate of termination transactions to generate threshold of necessary system resources.

For example, the process 400 may predict using one or more decision trees, based at least on the first transaction data, a number of transactions that will result in subsequent termination transactions in a given network time interval. In some implementations, the programmatically expected threshold of system resources is in the form of a currency volume.

In embodiments the first prediction value takes into account the one or more first attributes associated with the device rendered object. In embodiments, the first prediction value takes into account the one or more first attributes associated with the device rendered object, as a machine learning model generating the first prediction value has been trained using attributes associated with a plurality of device rendered objects and transactions and other data associated therewith.

Example Transaction Prediction Processes

FIG. 5A is a flow chart of an example process 500 a for training a termination transaction prediction model based on selected transaction attributes. The process 500 a begins with selecting first attributes from an attribute pool to generate a first decision tree, the first decision tree being a model for predicting termination transactions (502). For example, the process 500 a may select all “booking_month” attributes and the “location” attribute and/or other attributes or clusters of attributes. The selected first attributes are used to generate a decision tree for prediction a termination transaction. In some implementations, the selection is based on a machine learning algorithm. In some implementations, the attributes are selected based on statistical analysis of past performances. In some implementations, the pool of attributes comprises one or more of the list of exemplary attributes above. In some implementations, the pool of attributes includes one or more of the clustered attributes of Table A.

The process 500 a continues with selecting second attributes from the attribute pool to generate a second decision tree, the second attributes being different from the first attributes and the second decision tree being a model for predicting termination transactions (504). The second attributes are selected in a manner similar to step 502. In some implementations, the second attributes are different from the first attributes. The selected second attributes are then used to generate a second decision tree. In some implementations, the process 500 a continues with optional step 506 shown in phantom. The process 500 a may select third attributes from an attribute pool to generate a third decision tree, the third decision tree being a model for predicting termination transactions (506). In some implementations, the third attributes are different from the first and second attributes. In some implementations, the third attributes are then used to generate a decision tree. In some implementations, each generated tree is unique. In some implementations, additional trees are generated based on other selections of attributes. In some implementations, the process 500 a may generate trees based on unique attribute selections until a threshold number of trees are generated. In some implementations, the process 500 a may generate trees based on unique attribute selections until the classification model is stable and accurate.

FIG. 5B is a flow chart of an example process 500 b for predicting termination transactions, according to a model trained based on selected attributes. The process 500 b begins with determining, for a first transaction, a first prediction based on the first decision tree and the first attributes, the first prediction being a prediction that a termination transaction will follow the first transaction during a given network time period (508). For example, the process 500 b may determine a first prediction based on the “booking month” attributes and the “location” attribute and/or other attributes or clusters of attributes.

The process 500 b continues with determining, for the first transaction, a second prediction based on the second decision tree and the second attributes, the second prediction being a prediction that a termination transaction will follow the second transaction during a given network time period (510).

In some implementations, the process 500 b includes optional step 512 shown in phantom. The process 500 b may determining, for a first transaction, a third prediction based on the third decision tree and the third attributes, the third prediction being a prediction that a termination transaction will follow the first transaction during a given network time period (512). In some embodiments, the third prediction is different from the first prediction.

FIG. 6 illustrates an exemplary random forest model for use with the present system, according to one embodiment. The model includes features such as distance, the popularity of a category of service or product, whether the promotion relates to a service, whether the merchant has offered a promotion before, whether the type of promotion has a high history of refunds, and whether the product is available online.

The exemplary random forest 600 is composed of N trees, where N is a number. The prediction of the random forest is the average of the predictions from the N trees. The prediction from a tree is determined by a root node decision (e.g., attribute associated with booking month) and then traversing a logic path through the tree to a terminal leaf node based on the decision outcome determined at each successive node along the path. For example, in a model comprised of N trees where N is 5, the random forest prediction is the average of all of the trees. Based on a certain threshold, for example 0.5, the prediction is that a promotion transaction from a prior network time period will (“1”) or will not (“0”) result in a termination transaction in a future network time period. By way of further example, if a promotion transaction occurred in a month that was not associated with a holiday and is associated with a popular category, the promotion transaction may receive a score of “0.” As another example, if the promotion occurred in a month that is associated with being pre-holiday (e.g., November), and is a service (i.e., requires the customer to travel to the site), the transaction may receive a score of “1.” The exemplary random forest 1300 prediction is the average of the respective predictions from trees 1, 2, 3, 4, and 5. In one example, tree 1 results in a score of “1,” tree 2 results in a score of “0,” tree 3 results in a score of “0,” tree 4 results in a score of “0,” and tree 5 results in a score of “1.” The average of the scores is (1+1)/5 or 0.4. Assuming an exemplary threshold for a transaction is 0.5, (e.g., if the score is greater than or equal to 0.5, the transaction is considered likely to result in a termination transaction in the future network period), the transaction in this example is considered not likely to result in a termination transaction in the future network period.

Additional Implementation Details

Although an example processing system has been described in FIG. 2, implementations of the subject matter and the functional operations described herein can be implemented in other types of digital electronic circuitry, or in computer software, firmware, or hardware, including the structures disclosed in this specification and their structural equivalents, or in combinations of one or more of them.

Embodiments of the subject matter and the operations described herein can be implemented in digital electronic circuitry, or in computer software, firmware, or hardware, including the structures disclosed in this specification and their structural equivalents, or in combinations of one or more of them. Embodiments of the subject matter described herein can be implemented as one or more computer programs, i.e., one or more modules of computer program instructions, encoded on computer storage medium for execution by, or to control the operation of, information/data processing apparatus. Alternatively, or in addition, the program instructions can be encoded on an artificially-generated propagated signal, e.g., a machine-generated electrical, optical, or electromagnetic signal, which is generated to encode information/data for transmission to suitable receiver apparatus for execution by an information/data processing apparatus. A computer storage medium can be, or be included in, a computer-readable storage device, a computer-readable storage substrate, a random or serial access memory array or device, or a combination of one or more of them. Moreover, while a computer storage medium is not a propagated signal, a computer storage medium can be a source or destination of computer program instructions encoded in an artificially-generated propagated signal. The computer storage medium can also be, or be included in, one or more separate physical components or media (e.g., multiple CDs, disks, or other storage devices).

The operations described herein can be implemented as operations performed by an information/data processing apparatus on information/data stored on one or more computer-readable storage devices or received from other sources.

The term “data processing apparatus” encompasses all kinds of apparatus, devices, and machines for processing data, including by way of example a programmable processor, a computer, a system on a chip, or multiple ones, or combinations, of the foregoing. The apparatus can include special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit). The apparatus can also include, in addition to hardware, code that creates an execution environment for the computer program in question, e.g., code that constitutes processor firmware, a protocol stack, a database management system, an operating system, a cross-platform runtime environment, a virtual machine, or a combination of one or more of them. The apparatus and execution environment can realize various different computing model infrastructures, such as web services, distributed computing and grid computing infrastructures.

A computer program (also known as a program, software, software application, script, or code) can be written in any form of programming language, including compiled or interpreted languages, declarative or procedural languages, and it can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, object, or other unit suitable for use in a computing environment. A computer program may, but need not, correspond to a file in a file system. A program can be stored in a portion of a file that holds other programs or information/data (e.g., one or more scripts stored in a markup language document), in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files that store one or more modules, sub-programs, or portions of code). A computer program can be deployed to be executed on one computer or on multiple computers that are located at one site or distributed across multiple sites and interconnected by a communication network.

The processes and logic flows described herein can be performed by one or more programmable processors executing one or more computer programs to perform actions by operating on input information/data and generating output. Processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and any one or more processors of any kind of digital computer. Generally, a processor will receive instructions and information/data from a read-only memory or a random access memory or both. The essential elements of a computer are a processor for performing actions in accordance with instructions and one or more memory devices for storing instructions and data. Generally, a computer will also include, or be operatively coupled to receive information/data from or transfer information/data to, or both, one or more mass storage devices for storing data, e.g., magnetic, magneto-optical disks, or optical disks. However, a computer need not have such devices. Devices suitable for storing computer program instructions and information/data include all forms of non-volatile memory, media and memory devices, including by way of example semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks, e.g., internal hard disks or removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks. The processor and the memory can be supplemented by, or incorporated in, special purpose logic circuitry.

To provide for interaction with a user, embodiments of the subject matter described herein can be implemented on a computer having a display device, e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor, for displaying information/data to the user and a keyboard and a pointing device, e.g., a mouse or a trackball, by which the user can provide input to the computer. Other kinds of devices can be used to provide for interaction with a user as well; for example, feedback provided to the user can be any form of sensory feedback, e.g., visual feedback, auditory feedback, or tactile feedback; and input from the user can be received in any form, including acoustic, speech, or tactile input. In addition, a computer can interact with a user by sending documents to and receiving documents from a device that is used by the user; for example, by sending web pages to a web browser on a user's client device in response to requests received from the web browser.

Embodiments of the subject matter described herein can be implemented in a computing system that includes a back-end component, e.g., as an information/data server, or that includes a middleware component, e.g., an application server, or that includes a front-end component, e.g., a client computer having a graphical user interface or a web browser through which a user can interact with an implementation of the subject matter described herein, or any combination of one or more such back-end, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital information/data communication, e.g., a communication network. Examples of communication networks include a local area network (“LAN”) and a wide area network (“WAN”), an inter-network (e.g., the Internet), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks).

The computing system can include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. In some embodiments, a server transmits information/data (e.g., an HTML page) to a client device (e.g., for purposes of displaying information/data to and receiving user input from a user interacting with the client device). Information/data generated at the client device (e.g., a result of the user interaction) can be received from the client device at the server.

While this specification contains many specific implementation details, these should not be construed as limitations on the scope of any inventions or of what may be claimed, but rather as descriptions of features specific to particular embodiments of particular inventions. Certain features that are described herein in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination. Moreover, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a subcombination or variation of a subcombination.

Similarly, while operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing may be advantageous. Moreover, the separation of various system components in the embodiments described above should not be understood as requiring such separation in all embodiments, and it should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products.

Thus, particular embodiments of the subject matter have been described. Other embodiments are within the scope of the following claims. In some cases, the actions recited in the claims can be performed in a different order and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In certain implementations, multitasking and parallel processing may be advantageous.

CONCLUSION

Many modifications and other embodiments of the inventions set forth herein will come to mind to one skilled in the art to which these inventions pertain having the benefit of the teachings presented in the foregoing descriptions and the associated drawings. Therefore, it is to be understood that the inventions are not to be limited to the specific embodiments disclosed and that modifications and other embodiments are intended to be included within the scope of the appended claims. Although specific terms are employed herein, they are used in a generic and descriptive sense only and not for purposes of limitation. 

The invention claimed is:
 1. A system for predicting one or more transaction terminations associated with a plurality of device rendered objects, the system comprising a server communicably coupled with a communication network, the server having a processor, the processor, when executing computer-readable instructions, is configured to: receive first transaction data and second transaction data, the first transaction data comprising a first timestamp and the second transaction data comprising a second timestamp, wherein the first and second transaction data are associated with a device rendered object of the plurality of device rendered objects, the second transaction occurring subsequent to the first transaction; receive system transaction data, wherein the system transaction data comprises a plurality of attributes associated with a plurality of users, a network time interval and a system wide transaction count occurring during the network time interval; determine, using a clustering technique, one or more first attributes from the plurality of attributes associated with the system transaction data, the first transaction data, the second transaction data and the device rendered object; determine, based on the one or more first attributes associated with the first transaction data, the second transaction data, the device rendered object and the system transaction data, a first prediction value that indicates a programmatically expected number of system wide transaction terminations for a future network time interval; and responsive to determining that system resources are required to fulfill transaction terminations associated with the first prediction value exceeding a system resource allocation threshold, allocate a system resource volume for correcting transaction terminations during the future network time interval.
 2. The system of claim 1, wherein each transaction termination is associated with a required system resource allocation defining an aggregation of network assets that is allocated to be available for fulfillment of network asset requests.
 3. The system of claim 1, wherein the one or more first attributes include one or more of a category for the device rendered object, GPS coordinates associated with the device rendered object, historical data associated with the category of the first device rendered object, and historical data associated with other device rendered objects having the same category as the first device rendered object.
 4. The system of claim 1, wherein the processor is further configured to: receive third transaction data and fourth transaction data, the third transaction data comprising a third timestamp and the fourth transaction data comprising a fourth timestamp, wherein the third and fourth transaction data are associated with a second device rendered object of the plurality of device rendered objects, the fourth transaction occurring subsequent to the third transaction; determine, using the clustering technique, one or more second attributes from the plurality of attributes associated with the system transaction data, the third transaction data, the fourth transaction data and the second device rendered object; and determine, based on the one or more second attributes associated with the third transaction data, the fourth transaction data, the second device rendered object, and the system transaction data, a second prediction value that indicates a programmatically expected number of system wide transaction terminations for a future network time interval, the second prediction value different from the first prediction value.
 5. The system of claim 4, wherein the processor is further configured to: determine, based on values of second attributes different from the first attributes, a third prediction indicating a programmatically expected number of system wide transaction terminations for a future network time interval.
 6. The system of claim 1, wherein determining the first prediction is based on a machine learning model.
 7. The system of claim 1, wherein the second transaction data represents a transaction termination.
 8. The system of claim 7, wherein the fourth transaction data represents a transaction termination.
 9. The system of claim 3, wherein the one or more first attributes corresponds to historical data associated with the GPS coordinates associated with the first device rendered object.
 10. The system of claim 9, wherein the historical data comprises data associated with device rendered objects having GPS coordinates that differ from the GPS coordinates of the first device rendered object by a distance threshold.
 11. The system of claim 1, wherein the processor is further configured to transmit device rendered objects to a network asset requester device based on the first prediction value to influence a reduction in the programmatically expected number of termination transactions.
 12. An apparatus for predicting one or more transaction terminations associated with a plurality of device rendered objects, the apparatus comprising at least one processor and at least one memory including computer program code, the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus to: receive first transaction data and second transaction data, the first transaction data comprising a first timestamp and the second transaction data comprising a second timestamp, wherein the first and second transaction data are associated with a device rendered object of the plurality of device rendered objects, the second transaction occurring subsequent to the first transaction; receive system transaction data, wherein the system transaction data comprises a plurality of attributes associated with a plurality of users, a network time interval and a system transaction count occurring during the network time interval; determine, using a clustering technique, one or more first attributes from the plurality of attributes associated with the system transaction data, the first transaction data, the second transaction data and the device rendered object; determine, based on the one or more first attributes associated with the first transaction data, the second transaction data, the device rendered object and the system transaction data, a first prediction value that indicates a programmatically expected number of system wide transaction terminations for a future network time interval; and responsive to determining that system resources are required to fulfill transaction terminations associated with the first prediction value exceeding a system resource allocation threshold, allocate a system resource volume for correcting transaction terminations during the future network time interval.
 13. The apparatus of claim 12, wherein each transaction termination is associated with a required system resource allocation defining an aggregation of network assets that is allocated to be available for fulfillment of network asset requests.
 14. The apparatus of claim 12, wherein the one or more first attributes include one or more of a category for the device rendered object, GPS coordinates associated with the device rendered object, historical data associated with the category of the first device rendered object, and historical data associated with other device rendered objects having the same category as the first device rendered object.
 15. The apparatus of claim 12, wherein the processor is further configured to: receive third transaction data and fourth transaction data, the third transaction data comprising a third timestamp and the fourth transaction data comprising a fourth timestamp, wherein the third and fourth transaction data are associated with a second device rendered object of the plurality of device rendered objects, the fourth transaction occurring subsequent to the third transaction; determine, using the clustering technique, one or more second attributes from the plurality of attributes associated with the system transaction data, the third transaction data, the fourth transaction data and the second device rendered object; and determine, based on the one or more second attributes associated with the third transaction data, the fourth transaction data, the second device rendered object, and the system transaction data, a second prediction value that indicates a programmatically expected number of system wide transaction terminations for a future network time interval, the second prediction value different from the first prediction value.
 16. The apparatus of claim 15, wherein the processor is further configured to: determine, based on values of second attributes different from the first attributes, a third prediction indicating a programmatically expected number of transaction terminations for a future network time interval.
 17. The apparatus of claim 12, wherein determining the first prediction is based on a machine learning model.
 18. The apparatus of claim 12, wherein the second transaction data represents a transaction termination.
 19. The apparatus of claim 12, wherein the fourth transaction data represents a transaction termination.
 20. The apparatus of claim 12, wherein the historical data comprises data associated with device rendered objects having GPS coordinates that differ from GPS coordinates of the first device rendered object by a distance threshold.
 21. The apparatus of claim 12, wherein the processor is further configured to: transmit device rendered objects to a network asset requester device based on the first prediction value to influence a reduction in the programmatically expected number of termination transactions. 